Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a33c98361036840cfa32d41308a3a8c9e70ae0d44608922ab44660d273896f1

Tx prefix hash: 39441117d07d0e3a8fc2ce912b96a288e492d05a591859cf4a6b8173319dd0dd
Tx public key: f8fdc964840a180c5d31512805cd8cd39254e37c8c98299bc0b504a8ed730ee8
Timestamp: 1740005715 Timestamp [UCT]: 2025-02-19 22:55:15 Age [y:d:h:m:s]: 00:230:21:03:14
Block: 1222941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162724 RingCT/type: yes/0
Extra: 01f8fdc964840a180c5d31512805cd8cd39254e37c8c98299bc0b504a8ed730ee8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7123a8df08b2402d855c1af38b05d8c38ae5d5456925cdf3fa0ad2d050ef5d19 0.600000000000 1709796 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": 1222951, "vin": [ { "gen": { "height": 1222941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7123a8df08b2402d855c1af38b05d8c38ae5d5456925cdf3fa0ad2d050ef5d19" } } ], "extra": [ 1, 248, 253, 201, 100, 132, 10, 24, 12, 93, 49, 81, 40, 5, 205, 140, 211, 146, 84, 227, 124, 140, 152, 41, 155, 192, 181, 4, 168, 237, 115, 14, 232, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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