Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a566589f47c6522bca9b47790384aef1977cdbe1b36b02908b0cdc94f7a59065

Tx prefix hash: e0948b94656418b14b3ea72ba228969b6eda0590e9c959b5a51f6d8ccb613659
Tx public key: 33d33fff1c32ebbb1de214ac49da16774e65f16142e5e5f2b03d8f09fd84c2ae
Timestamp: 1741182863 Timestamp [UCT]: 2025-03-05 13:54:23 Age [y:d:h:m:s]: 00:261:03:24:24
Block: 1232716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184374 RingCT/type: yes/0
Extra: 0133d33fff1c32ebbb1de214ac49da16774e65f16142e5e5f2b03d8f09fd84c2ae0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696acbf19a20f3427a986d11b9b2f10e69ca6b4988ca61b0421396c5e8befc56 0.600000000000 1719629 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": 1232726, "vin": [ { "gen": { "height": 1232716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696acbf19a20f3427a986d11b9b2f10e69ca6b4988ca61b0421396c5e8befc56" } } ], "extra": [ 1, 51, 211, 63, 255, 28, 50, 235, 187, 29, 226, 20, 172, 73, 218, 22, 119, 78, 101, 241, 97, 66, 229, 229, 242, 176, 61, 143, 9, 253, 132, 194, 174, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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