Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569cb25f221ab1113131e48b2362da7818dfcbfd4a210ffe20383b2b7ffa9260

Tx prefix hash: 10a2b54dfb48983df59e0b77ea5bfab2265a2d6a65e1116058d0ca3980f18da9
Tx public key: 72f87b712f0b3e144e07835c20912e2b561e8e4c023f7d1414df0ecf34c21121
Timestamp: 1715907872 Timestamp [UCT]: 2024-05-17 01:04:32 Age [y:d:h:m:s]: 00:167:23:37:00
Block: 1023637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120246 RingCT/type: yes/0
Extra: 0172f87b712f0b3e144e07835c20912e2b561e8e4c023f7d1414df0ecf34c2112102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5db110abb3327ed860b4cc087b929452180556a5eb27038aeac5513f39e271d 0.600000000000 1488760 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": 1023647, "vin": [ { "gen": { "height": 1023637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5db110abb3327ed860b4cc087b929452180556a5eb27038aeac5513f39e271d" } } ], "extra": [ 1, 114, 248, 123, 113, 47, 11, 62, 20, 78, 7, 131, 92, 32, 145, 46, 43, 86, 30, 142, 76, 2, 63, 125, 20, 20, 223, 14, 207, 52, 194, 17, 33, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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