Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c67ebf51b3eb0de06937cf896d19387a4d6a6592786a09f3333f04b16610746c

Tx prefix hash: ab8853362ecdcdf3ea18006818bc066acd847bc59889a323fa5fd3c3709cdf6a
Tx public key: dbf1178058e55d4f5419a3146293e5d56dbc8b3169c30f58176c661c68a4bc0d
Timestamp: 1694263679 Timestamp [UCT]: 2023-09-09 12:47:59 Age [y:d:h:m:s]: 01:133:21:34:24
Block: 844365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356984 RingCT/type: yes/0
Extra: 01dbf1178058e55d4f5419a3146293e5d56dbc8b3169c30f58176c661c68a4bc0d0211000000054b8f5122000000000000000000

1 output(s) for total of 0.977841145000 dcy

stealth address amount amount idx
00: e7b4669c5115991131cc92a130b5724b8fecc0f4642c7fe2fd01fb75cc7a5079 0.977841145000 1297669 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": 844375, "vin": [ { "gen": { "height": 844365 } } ], "vout": [ { "amount": 977841145, "target": { "key": "e7b4669c5115991131cc92a130b5724b8fecc0f4642c7fe2fd01fb75cc7a5079" } } ], "extra": [ 1, 219, 241, 23, 128, 88, 229, 93, 79, 84, 25, 163, 20, 98, 147, 229, 213, 109, 188, 139, 49, 105, 195, 15, 88, 23, 108, 102, 28, 104, 164, 188, 13, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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