Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dcff9547109c746754f96cbaf66b331f061f167b4f43cfef471b45da695b33a

Tx prefix hash: 4db5720df526c8c20b44e04ae2debd7648ea3d818e8cd511de478d77b1626d25
Tx public key: 3323d23d410388b3e37fe53329402555d66b84250bb5f6c505359c2ff0cbea08
Timestamp: 1704067497 Timestamp [UCT]: 2024-01-01 00:04:57 Age [y:d:h:m:s]: 01:153:09:57:18
Block: 925463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370802 RingCT/type: yes/0
Extra: 013323d23d410388b3e37fe53329402555d66b84250bb5f6c505359c2ff0cbea080211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11ca1989ad1d38c614dfda0fdf964ab937c0217dd6f0e5c4405a032ff6e923ef 0.600000000000 1383225 of 15

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": 925473, "vin": [ { "gen": { "height": 925463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11ca1989ad1d38c614dfda0fdf964ab937c0217dd6f0e5c4405a032ff6e923ef" } } ], "extra": [ 1, 51, 35, 210, 61, 65, 3, 136, 179, 227, 127, 229, 51, 41, 64, 37, 85, 214, 107, 132, 37, 11, 181, 246, 197, 5, 53, 156, 47, 240, 203, 234, 8, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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