Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f34462e73f1a40093c6034a4d9b533202190de55154c8381375c60e3f320145d

Tx prefix hash: 5b0eb403a02a54ce2975489a5c1bf1f7b012132038400b16bd466160a2e451a4
Tx public key: dc2265fd097b7cc4f8d81a6a18c7506c5262f2195f92c96523096b0df3c6c540
Timestamp: 1746398556 Timestamp [UCT]: 2025-05-04 22:42:36 Age [y:d:h:m:s]: 00:195:20:45:47
Block: 1275889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137694 RingCT/type: yes/0
Extra: 01dc2265fd097b7cc4f8d81a6a18c7506c5262f2195f92c96523096b0df3c6c54002110000000a1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ef9474a2de36179cce64117a00d0878040a653b771b9af1bbc7a99430fe82ca 0.600000000000 1763204 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": 1275899, "vin": [ { "gen": { "height": 1275889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ef9474a2de36179cce64117a00d0878040a653b771b9af1bbc7a99430fe82ca" } } ], "extra": [ 1, 220, 34, 101, 253, 9, 123, 124, 196, 248, 216, 26, 106, 24, 199, 80, 108, 82, 98, 242, 25, 95, 146, 201, 101, 35, 9, 107, 13, 243, 198, 197, 64, 2, 17, 0, 0, 0, 10, 31, 144, 81, 122, 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