Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ed72c3c29da700b54664719b59da063cf41302d197d8475245737d62803d421

Tx prefix hash: a8f8f63ccd0683d1b41389c1457ff25afb50cae2d3276a74bd2f3b1d2d909ce6
Tx public key: 8cf631c1a4d62d693cea96609b760208722f3aae76f8c18b2f8c30e3d3615bc2
Timestamp: 1706910552 Timestamp [UCT]: 2024-02-02 21:49:12 Age [y:d:h:m:s]: 01:281:20:43:13
Block: 949022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460237 RingCT/type: yes/0
Extra: 018cf631c1a4d62d693cea96609b760208722f3aae76f8c18b2f8c30e3d3615bc20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6853aa5a9973c4ddf337cd4023922310cd550d2bd76f34178f0c52a74a3b259 0.600000000000 1407544 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": 949032, "vin": [ { "gen": { "height": 949022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6853aa5a9973c4ddf337cd4023922310cd550d2bd76f34178f0c52a74a3b259" } } ], "extra": [ 1, 140, 246, 49, 193, 164, 214, 45, 105, 60, 234, 150, 96, 155, 118, 2, 8, 114, 47, 58, 174, 118, 248, 193, 139, 47, 140, 48, 227, 211, 97, 91, 194, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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