Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6f8939ded620894ac246fef2d0b263cd6bbd66e62f5015bfe1c6a7abe28199

Tx prefix hash: 33d2dd4261a224137dc7d5d27a68731ad43606b5f0e6fb1ece71c920a848001b
Tx public key: 989e0dcc3f16c41d75bf0a3783d440fe22501e53c2a4fc4c725fcbde491b8063
Timestamp: 1721901809 Timestamp [UCT]: 2024-07-25 10:03:29 Age [y:d:h:m:s]: 00:277:01:15:42
Block: 1073313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197950 RingCT/type: yes/0
Extra: 01989e0dcc3f16c41d75bf0a3783d440fe22501e53c2a4fc4c725fcbde491b8063021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a5cb9e05a9dda3b99e0e65edcfcd41eb129e8db5acd876de4b97122b96aa12 0.600000000000 1545812 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": 1073323, "vin": [ { "gen": { "height": 1073313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a5cb9e05a9dda3b99e0e65edcfcd41eb129e8db5acd876de4b97122b96aa12" } } ], "extra": [ 1, 152, 158, 13, 204, 63, 22, 196, 29, 117, 191, 10, 55, 131, 212, 64, 254, 34, 80, 30, 83, 194, 164, 252, 76, 114, 95, 203, 222, 73, 27, 128, 99, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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