Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4449995757ee3281aee65c24330c56968857e24d3ef70100562c4ea603a569a0

Tx prefix hash: 34ff940e9a2a3be0a6e74a98f0e4dc2cb1d4947427473afc27aa8d9a1cb836b4
Tx public key: 311a13410fb107c28b2a582e62dde22ae0ed13e442fb506f40e96f70afbec058
Timestamp: 1721493390 Timestamp [UCT]: 2024-07-20 16:36:30 Age [y:d:h:m:s]: 00:243:01:13:13
Block: 1069934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173646 RingCT/type: yes/0
Extra: 01311a13410fb107c28b2a582e62dde22ae0ed13e442fb506f40e96f70afbec058021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2afc532874de7a6e20de25e662db4df700c4a9e60521aa98ff791241ad7c103a 0.600000000000 1541559 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": 1069944, "vin": [ { "gen": { "height": 1069934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2afc532874de7a6e20de25e662db4df700c4a9e60521aa98ff791241ad7c103a" } } ], "extra": [ 1, 49, 26, 19, 65, 15, 177, 7, 194, 139, 42, 88, 46, 98, 221, 226, 42, 224, 237, 19, 228, 66, 251, 80, 111, 64, 233, 111, 112, 175, 190, 192, 88, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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