Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cde031555eed46807dcb4c9210ee723ffcf26bb57f0c27aeb2bf2f0544d5ae7

Tx prefix hash: d0af89c8c5f6d4a03aae5a2afea165091585be53dd7d2f52d680a6d3058d4f24
Tx public key: 8157ed52567cfe5c15da8bf805a79e920621e191290e3109b0fed5ffba3219b5
Timestamp: 1730118942 Timestamp [UCT]: 2024-10-28 12:35:42 Age [y:d:h:m:s]: 00:086:03:15:40
Block: 1141374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61573 RingCT/type: yes/0
Extra: 018157ed52567cfe5c15da8bf805a79e920621e191290e3109b0fed5ffba3219b5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008c8b244edb9fc3e2dcb5ed2138bc872f8bf8c8cc33a1615b7639992bef9791 0.600000000000 1625181 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": 1141384, "vin": [ { "gen": { "height": 1141374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008c8b244edb9fc3e2dcb5ed2138bc872f8bf8c8cc33a1615b7639992bef9791" } } ], "extra": [ 1, 129, 87, 237, 82, 86, 124, 254, 92, 21, 218, 139, 248, 5, 167, 158, 146, 6, 33, 225, 145, 41, 14, 49, 9, 176, 254, 213, 255, 186, 50, 25, 181, 2, 17, 0, 0, 0, 3, 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