Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17471b6f3d3447347dea01801453fd2f608ae302260369f2f706fc8c423aae31

Tx prefix hash: 476c9067e1ec1b8facf1b8e05f49d80bde1f2a883a81af3df457904f5a249dfa
Tx public key: c24254f471c6b0cf6fd7e81d606ddf20bb8ad4e099fe7ee533af44890fa37a4a
Timestamp: 1711722744 Timestamp [UCT]: 2024-03-29 14:32:24 Age [y:d:h:m:s]: 01:064:02:35:10
Block: 988952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306806 RingCT/type: yes/0
Extra: 01c24254f471c6b0cf6fd7e81d606ddf20bb8ad4e099fe7ee533af44890fa37a4a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caec5fc454ceb5c7ac6545967829095d1682ff74f695a4e945fc8bd93d7ba60c 0.600000000000 1449243 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": 988962, "vin": [ { "gen": { "height": 988952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caec5fc454ceb5c7ac6545967829095d1682ff74f695a4e945fc8bd93d7ba60c" } } ], "extra": [ 1, 194, 66, 84, 244, 113, 198, 176, 207, 111, 215, 232, 29, 96, 109, 223, 32, 187, 138, 212, 224, 153, 254, 126, 229, 51, 175, 68, 137, 15, 163, 122, 74, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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