Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac8b1dc4bdd7f39eae4c91f5106ebcceee76ce8b19aea508cfd4894b19504547

Tx prefix hash: 86fb1414749d5b8c4032001f74f812682f9bd9752fc632ae849baeb338503b0e
Tx public key: 756ed8dd820b9bf3f12efb961a9d27ded4a4420baa56193001a034adbedff4e1
Timestamp: 1577729820 Timestamp [UCT]: 2019-12-30 18:17:00 Age [y:d:h:m:s]: 05:132:03:54:50
Block: 35228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244218 RingCT/type: yes/0
Extra: 01756ed8dd820b9bf3f12efb961a9d27ded4a4420baa56193001a034adbedff4e10211000000054ac5aa02000000000000000000

1 output(s) for total of 469.111270171000 dcy

stealth address amount amount idx
00: ee4617f89cd8c25d4e3d7bb3f6df28f400e34679830d05dee2c25b7124d0a181 469.111270171000 59330 of 0

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": 35238, "vin": [ { "gen": { "height": 35228 } } ], "vout": [ { "amount": 469111270171, "target": { "key": "ee4617f89cd8c25d4e3d7bb3f6df28f400e34679830d05dee2c25b7124d0a181" } } ], "extra": [ 1, 117, 110, 216, 221, 130, 11, 155, 243, 241, 46, 251, 150, 26, 157, 39, 222, 212, 164, 66, 11, 170, 86, 25, 48, 1, 160, 52, 173, 190, 223, 244, 225, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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