Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a1f162769d58c939a4a728b1e2d3e0914ca9579021273df007d9662d80e4b923

Tx prefix hash: 880c66fe6b7f507559b1f8834f93646b843f78a86f3950c07ce4fb4f13f2e3a0
Tx public key: 0d5d27c17e6748e35da68f2eb65164391414d3b7c217a949dfe0ce4dd8d4ed9d
Timestamp: 1681151002 Timestamp [UCT]: 2023-04-10 18:23:22 Age [y:d:h:m:s]: 01:157:09:59:09
Block: 735712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373965 RingCT/type: yes/0
Extra: 010d5d27c17e6748e35da68f2eb65164391414d3b7c217a949dfe0ce4dd8d4ed9d021100000003b3164c24000000000000000000

1 output(s) for total of 2.240169910000 dcy

stealth address amount amount idx
00: cc3826854277b14811bec90aca4d98ad63249b3a5eea38c8f0a9c9880acc22f2 2.240169910000 1182063 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 735722, "vin": [ { "gen": { "height": 735712 } } ], "vout": [ { "amount": 2240169910, "target": { "key": "cc3826854277b14811bec90aca4d98ad63249b3a5eea38c8f0a9c9880acc22f2" } } ], "extra": [ 1, 13, 93, 39, 193, 126, 103, 72, 227, 93, 166, 143, 46, 182, 81, 100, 57, 20, 20, 211, 183, 194, 23, 169, 73, 223, 224, 206, 77, 216, 212, 237, 157, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8