Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d6cc86fd1dd4479ab6e6ae8037ee4b5b47ccd11fc9726b01da341f09c6f683

Tx prefix hash: 886cbd3d7f37cbc02c33c7f476c38fc126ddc438eeb885fee39f9d5f694bd1b0
Tx public key: 464f355c1ac298503fbd2d73102c904d44778b4ec64f54f0c7e546ed29e3fa3c
Timestamp: 1736769787 Timestamp [UCT]: 2025-01-13 12:03:07 Age [y:d:h:m:s]: 00:067:23:49:07
Block: 1196442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48372 RingCT/type: yes/0
Extra: 01464f355c1ac298503fbd2d73102c904d44778b4ec64f54f0c7e546ed29e3fa3c02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f10b0411005e0810a89a4a0c69a4b7c70229417ef50cc420d56f230deae57898 0.600000000000 1683041 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": 1196452, "vin": [ { "gen": { "height": 1196442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f10b0411005e0810a89a4a0c69a4b7c70229417ef50cc420d56f230deae57898" } } ], "extra": [ 1, 70, 79, 53, 92, 26, 194, 152, 80, 63, 189, 45, 115, 16, 44, 144, 77, 68, 119, 139, 78, 198, 79, 84, 240, 199, 229, 70, 237, 41, 227, 250, 60, 2, 17, 0, 0, 0, 11, 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