Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf733940667ebf29e63701447649b0927d72bcec2ab3fae81ced57d9b14b5ee0

Tx prefix hash: 62a689ac461602dd9718db97786e24973a7cc144a1f4cb18cf504d5b4d9b034d
Tx public key: dc2324f18d955c5d06ba6ab1c4ca8b1b2328eefadc0382da41c9c71965f88e3a
Timestamp: 1760656738 Timestamp [UCT]: 2025-10-16 23:18:58 Age [y:d:h:m:s]: 00:035:13:59:13
Block: 1391511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25454 RingCT/type: yes/0
Extra: 01dc2324f18d955c5d06ba6ab1c4ca8b1b2328eefadc0382da41c9c71965f88e3a0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a5e9cc569d95d2010aec7aa5a4b69896277b5a00ab97f16bbb1b3d3db8a448 0.600000000000 1879758 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": 1391521, "vin": [ { "gen": { "height": 1391511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a5e9cc569d95d2010aec7aa5a4b69896277b5a00ab97f16bbb1b3d3db8a448" } } ], "extra": [ 1, 220, 35, 36, 241, 141, 149, 92, 93, 6, 186, 106, 177, 196, 202, 139, 27, 35, 40, 238, 250, 220, 3, 130, 218, 65, 201, 199, 25, 101, 248, 142, 58, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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