Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd5ded717ed7478899b6a8d12d3de68bdf0ed0df6d57f8ca5e44899b6cb37dff

Tx prefix hash: f85405c5f90c155371b9f511b10a37e4790438ccb2e966bc50ea14158d2d13d2
Tx public key: 13c84a5846be3944a335a0b383ba89f121c8de0582c19e228aed6e49bfdb39dd
Timestamp: 1714148838 Timestamp [UCT]: 2024-04-26 16:27:18 Age [y:d:h:m:s]: 00:348:22:17:18
Block: 1009047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249438 RingCT/type: yes/0
Extra: 0113c84a5846be3944a335a0b383ba89f121c8de0582c19e228aed6e49bfdb39dd0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e93bb30fbe59e953ab4382d3e4a5a1d633a5cc63d01b8dfd23a642ab2e885a 0.600000000000 1470601 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": 1009057, "vin": [ { "gen": { "height": 1009047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e93bb30fbe59e953ab4382d3e4a5a1d633a5cc63d01b8dfd23a642ab2e885a" } } ], "extra": [ 1, 19, 200, 74, 88, 70, 190, 57, 68, 163, 53, 160, 179, 131, 186, 137, 241, 33, 200, 222, 5, 130, 193, 158, 34, 138, 237, 110, 73, 191, 219, 57, 221, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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