Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b9a2f34adc77b47a6b81ee215673bb3c967f9fc67fd084902099c61c0c2298

Tx prefix hash: 878baec8ef9d1ec3a872524822a51fe876e1df7d3560da9ac21de2cde06dd04c
Tx public key: c96ef151283d2ff0e9b099129d52c62bd63c895b7e33f0ff5b985db7d6a61822
Timestamp: 1740840384 Timestamp [UCT]: 2025-03-01 14:46:24 Age [y:d:h:m:s]: 00:263:17:15:05
Block: 1229866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186241 RingCT/type: yes/0
Extra: 01c96ef151283d2ff0e9b099129d52c62bd63c895b7e33f0ff5b985db7d6a61822021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 297a77b062316bd892b59e342a8ee9aa31fc76f7126073aa0619da59d6880d14 0.600000000000 1716757 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": 1229876, "vin": [ { "gen": { "height": 1229866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "297a77b062316bd892b59e342a8ee9aa31fc76f7126073aa0619da59d6880d14" } } ], "extra": [ 1, 201, 110, 241, 81, 40, 61, 47, 240, 233, 176, 153, 18, 157, 82, 198, 43, 214, 60, 137, 91, 126, 51, 240, 255, 91, 152, 93, 183, 214, 166, 24, 34, 2, 17, 0, 0, 0, 6, 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