Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c19cbfa8f0c432489b8c14b493b20950795d7f440942158fc691f2dbb964ae31

Tx prefix hash: ab7ab236815877802f2ac7544f4510fba1ef2c36ea713344ceb05b5e33cce2ed
Tx public key: a4fc5d1fad9c13541adec382b385d6b423e2c54927dadd82326a43cb22d7688d
Timestamp: 1731404910 Timestamp [UCT]: 2024-11-12 09:48:30 Age [y:d:h:m:s]: 00:139:12:36:54
Block: 1152014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99543 RingCT/type: yes/0
Extra: 01a4fc5d1fad9c13541adec382b385d6b423e2c54927dadd82326a43cb22d7688d02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9a1f8953841c5d5b2a89e81a9823576bdff1aebd65bf75f31c170ab38370aa 0.600000000000 1637605 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": 1152024, "vin": [ { "gen": { "height": 1152014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9a1f8953841c5d5b2a89e81a9823576bdff1aebd65bf75f31c170ab38370aa" } } ], "extra": [ 1, 164, 252, 93, 31, 173, 156, 19, 84, 26, 222, 195, 130, 179, 133, 214, 180, 35, 226, 197, 73, 39, 218, 221, 130, 50, 106, 67, 203, 34, 215, 104, 141, 2, 17, 0, 0, 0, 12, 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