Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2747f5a325276d783dfd18216d6943251d941a779e5e8dae0b805729cc6fd919

Tx prefix hash: 182ea4c1737bb9e2588b8c41e77689d6556f8144168b875ad13ee2b9dc300ab5
Tx public key: 25e6ebdc6d43a0c4869227031542d80274957e5405b0a98c1c86dd00503d899d
Timestamp: 1706570691 Timestamp [UCT]: 2024-01-29 23:24:51 Age [y:d:h:m:s]: 01:289:09:27:35
Block: 946200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465640 RingCT/type: yes/0
Extra: 0125e6ebdc6d43a0c4869227031542d80274957e5405b0a98c1c86dd00503d899d02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: decfa1706f1c5a9a0a6505202f54e2ab0ade7a7228c145b6c7011bed06f8fb25 0.600000000000 1404530 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": 946210, "vin": [ { "gen": { "height": 946200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "decfa1706f1c5a9a0a6505202f54e2ab0ade7a7228c145b6c7011bed06f8fb25" } } ], "extra": [ 1, 37, 230, 235, 220, 109, 67, 160, 196, 134, 146, 39, 3, 21, 66, 216, 2, 116, 149, 126, 84, 5, 176, 169, 140, 28, 134, 221, 0, 80, 61, 137, 157, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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