Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c96dfdffa106aa71cbc324c0f471c78934975aafdf80ca388616e1fd2526f1e

Tx prefix hash: a7e2ff6ef49a2009b5bf3dcde5b4dc1a0f3aeee44b1cace9be308db0b488bca1
Tx public key: 490e00ad1645c8ca9af6a22920fe350fe9bd7b7c3e2e781f0976833484c22f16
Timestamp: 1757129564 Timestamp [UCT]: 2025-09-06 03:32:44 Age [y:d:h:m:s]: 00:088:15:26:53
Block: 1362352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63405 RingCT/type: yes/0
Extra: 01490e00ad1645c8ca9af6a22920fe350fe9bd7b7c3e2e781f0976833484c22f16021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c307bbfa6cd9a23560ada014cb8adbeb0f05248197309d87fa6b637c09cb9c 0.600000000000 1850383 of 15

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": 1362362, "vin": [ { "gen": { "height": 1362352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c307bbfa6cd9a23560ada014cb8adbeb0f05248197309d87fa6b637c09cb9c" } } ], "extra": [ 1, 73, 14, 0, 173, 22, 69, 200, 202, 154, 246, 162, 41, 32, 254, 53, 15, 233, 189, 123, 124, 62, 46, 120, 31, 9, 118, 131, 52, 132, 194, 47, 22, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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