Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 175511a088d33420578d028e97273512f1abdb1228ccc5d6400df33ac207d617

Tx prefix hash: f398cd6b55762f7bf980a9e723557facae096e6f49c329c21dc289f62c696bfb
Tx public key: 9e1aa8dc85c66bbc74e45c458916e5c4a5f8370270511754b39a0c1e7302c4eb
Timestamp: 1666450625 Timestamp [UCT]: 2022-10-22 14:57:05 Age [y:d:h:m:s]: 02:154:09:47:21
Block: 614612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631996 RingCT/type: yes/0
Extra: 019e1aa8dc85c66bbc74e45c458916e5c4a5f8370270511754b39a0c1e7302c4eb021100000001faf35c9c000000000000000000

1 output(s) for total of 5.643328674000 dcy

stealth address amount amount idx
00: 44ff088ccf9958ebd17a1f138bdced83e0a9712d0a0dd5ff164320f163701f16 5.643328674000 1052009 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": 614622, "vin": [ { "gen": { "height": 614612 } } ], "vout": [ { "amount": 5643328674, "target": { "key": "44ff088ccf9958ebd17a1f138bdced83e0a9712d0a0dd5ff164320f163701f16" } } ], "extra": [ 1, 158, 26, 168, 220, 133, 198, 107, 188, 116, 228, 92, 69, 137, 22, 229, 196, 165, 248, 55, 2, 112, 81, 23, 84, 179, 154, 12, 30, 115, 2, 196, 235, 2, 17, 0, 0, 0, 1, 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