Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55b960ca4124a0443a17f8dbb2e30e9635badfa4e05ad2deac8963f9cab3570e

Tx prefix hash: 47ca9069aa0f1663d6d1e2e253ba224bd954565b1a150f205c922bc2596c0f00
Tx public key: c043faffdf1356d9077caacc2e3b8abf528114ba3dd11e33596f6906c815495d
Timestamp: 1710559761 Timestamp [UCT]: 2024-03-16 03:29:21 Age [y:d:h:m:s]: 01:002:12:10:51
Block: 979308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262772 RingCT/type: yes/0
Extra: 01c043faffdf1356d9077caacc2e3b8abf528114ba3dd11e33596f6906c815495d02110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcce480e3ce194cfe05c46584b5b4f843a2c40e3162ae53e097fa330aab4d683 0.600000000000 1439341 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": 979318, "vin": [ { "gen": { "height": 979308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcce480e3ce194cfe05c46584b5b4f843a2c40e3162ae53e097fa330aab4d683" } } ], "extra": [ 1, 192, 67, 250, 255, 223, 19, 86, 217, 7, 124, 170, 204, 46, 59, 138, 191, 82, 129, 20, 186, 61, 209, 30, 51, 89, 111, 105, 6, 200, 21, 73, 93, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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