Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc8379fff35722dae0ebc0308b1803add123c92818d3d71ff2969e225731ea7

Tx prefix hash: f3413a9be37b43313670e2b1032a87586d21b4f8e2e82f745abf76bc7edd3b3c
Tx public key: 0dea02007499c3b5557a22393b80d57afe9d48a7b7db9a2e8921e9e07d973343
Timestamp: 1728082897 Timestamp [UCT]: 2024-10-04 23:01:37 Age [y:d:h:m:s]: 00:236:05:05:27
Block: 1124564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168666 RingCT/type: yes/0
Extra: 010dea02007499c3b5557a22393b80d57afe9d48a7b7db9a2e8921e9e07d973343021100000004e914dd15000000000000000000

1 output(s) for total of 0.606000000000 dcy

stealth address amount amount idx
00: dbb287ca607719fec1a9dabcc4565d483231191ed2cc45f505dec3d56ff4a526 0.606000000000 1607205 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": 1124574, "vin": [ { "gen": { "height": 1124564 } } ], "vout": [ { "amount": 606000000, "target": { "key": "dbb287ca607719fec1a9dabcc4565d483231191ed2cc45f505dec3d56ff4a526" } } ], "extra": [ 1, 13, 234, 2, 0, 116, 153, 195, 181, 85, 122, 34, 57, 59, 128, 213, 122, 254, 157, 72, 167, 183, 219, 154, 46, 137, 33, 233, 224, 125, 151, 51, 67, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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