Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97fc58800b7bd67e1d6ecdcd86ee1efdd9308eaae801bfa65ba1109a0e8768d

Tx prefix hash: 273627d0215357fd966404c64cb404dfb9dc00b43128f479fe2d424459d78f80
Tx public key: 0bf2e4c733980ea92deeb7dd3b0caa92825cfcf6bc41a163c4bfe13e35225db0
Timestamp: 1699827388 Timestamp [UCT]: 2023-11-12 22:16:28 Age [y:d:h:m:s]: 01:080:00:36:47
Block: 890322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318333 RingCT/type: yes/0
Extra: 010bf2e4c733980ea92deeb7dd3b0caa92825cfcf6bc41a163c4bfe13e35225db0021100000003faf35c9c000000000000000000

1 output(s) for total of 0.688642182000 dcy

stealth address amount amount idx
00: 569a4159dec9a88a9f976678637ad610fbe8e64480453482d05d84e22880e458 0.688642182000 1346345 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": 890332, "vin": [ { "gen": { "height": 890322 } } ], "vout": [ { "amount": 688642182, "target": { "key": "569a4159dec9a88a9f976678637ad610fbe8e64480453482d05d84e22880e458" } } ], "extra": [ 1, 11, 242, 228, 199, 51, 152, 14, 169, 45, 238, 183, 221, 59, 12, 170, 146, 130, 92, 252, 246, 188, 65, 161, 99, 196, 191, 225, 62, 53, 34, 93, 176, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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