Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13195e4b0a3b85fe8b3e66d56f179287c1ce37f08a384e3e68a6f1bcb5a53276

Tx prefix hash: 40a1c12a74791ca3d0c7ca482a5636909070a827b442da17aede21551627e489
Tx public key: 9c9d61bb1f58e83b7b5bb9317360d9e33d1faea3fe047eb8e54dce547c5f9cb3
Timestamp: 1698499099 Timestamp [UCT]: 2023-10-28 13:18:19 Age [y:d:h:m:s]: 01:160:17:53:24
Block: 879526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375865 RingCT/type: yes/0
Extra: 019c9d61bb1f58e83b7b5bb9317360d9e33d1faea3fe047eb8e54dce547c5f9cb302110000001433af99f4000000000000000000

1 output(s) for total of 0.747765229000 dcy

stealth address amount amount idx
00: eb6fe526801b1e85464c55b961747aec84fed8eeb1b5106b41fd54513eb26cd7 0.747765229000 1335054 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": 879536, "vin": [ { "gen": { "height": 879526 } } ], "vout": [ { "amount": 747765229, "target": { "key": "eb6fe526801b1e85464c55b961747aec84fed8eeb1b5106b41fd54513eb26cd7" } } ], "extra": [ 1, 156, 157, 97, 187, 31, 88, 232, 59, 123, 91, 185, 49, 115, 96, 217, 227, 61, 31, 174, 163, 254, 4, 126, 184, 229, 77, 206, 84, 124, 95, 156, 179, 2, 17, 0, 0, 0, 20, 51, 175, 153, 244, 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