Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b72cb03d4aabd1c27829f0bd89a509e643f0de48ef800b62706fd516b6cadf1

Tx prefix hash: 0bfcbc30b8bf53fe65d0cb6a468f85f3d2a810b289a7ec901eb01159d7f6737b
Tx public key: c2daa68b5de9473413753615cfb0eac26b9a93b8c368c90f70bb72266f0c6d31
Timestamp: 1735341420 Timestamp [UCT]: 2024-12-27 23:17:00 Age [y:d:h:m:s]: 00:328:02:20:32
Block: 1184607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232010 RingCT/type: yes/0
Extra: 01c2daa68b5de9473413753615cfb0eac26b9a93b8c368c90f70bb72266f0c6d31021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a54a7937c9ca769217515feaeaa81ed4437e685e837e1a9b7d1049b6bc4b1937 0.600000000000 1671066 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": 1184617, "vin": [ { "gen": { "height": 1184607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54a7937c9ca769217515feaeaa81ed4437e685e837e1a9b7d1049b6bc4b1937" } } ], "extra": [ 1, 194, 218, 166, 139, 93, 233, 71, 52, 19, 117, 54, 21, 207, 176, 234, 194, 107, 154, 147, 184, 195, 104, 201, 15, 112, 187, 114, 38, 111, 12, 109, 49, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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