Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0556ed765343f978af69776dc5ae3cdb2a41e4c668e9ee7d00b79900b402574a

Tx prefix hash: 1c361f89fefc37bd564f9d5aa335e03c277550c454e62f5c6584ab0bb2f29e82
Tx public key: 2ff30e34e12570be4fa96b9b40f12a68975d0fa331a5429dc2745986c467a71b
Timestamp: 1724644250 Timestamp [UCT]: 2024-08-26 03:50:50 Age [y:d:h:m:s]: 00:274:13:43:51
Block: 1096056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196135 RingCT/type: yes/0
Extra: 012ff30e34e12570be4fa96b9b40f12a68975d0fa331a5429dc2745986c467a71b02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deadc4c3ae52505c0d3ac7dc053d27caa206ed0f9dee9b40a784eea54a4eb2c7 0.600000000000 1571243 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": 1096066, "vin": [ { "gen": { "height": 1096056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deadc4c3ae52505c0d3ac7dc053d27caa206ed0f9dee9b40a784eea54a4eb2c7" } } ], "extra": [ 1, 47, 243, 14, 52, 225, 37, 112, 190, 79, 169, 107, 155, 64, 241, 42, 104, 151, 93, 15, 163, 49, 165, 66, 157, 194, 116, 89, 134, 196, 103, 167, 27, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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