Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6adb277690cb12979df1366e9d03e8c23180e951b1a3de14f5b4358c3011bcf8

Tx prefix hash: 2bdfe8adee3639d551150d68a0a2223291fc14acc417b8492e891a712b49ef83
Tx public key: 0353c7d4adceff291e163ff029848e0a2b8caf5a0fa97760d0d86314085e8f02
Timestamp: 1729795986 Timestamp [UCT]: 2024-10-24 18:53:06 Age [y:d:h:m:s]: 00:146:03:22:55
Block: 1138727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104270 RingCT/type: yes/0
Extra: 010353c7d4adceff291e163ff029848e0a2b8caf5a0fa97760d0d86314085e8f02021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99320536eac617352ea4c47007417c68f8d226fde509e60b5f531fd0b739fba7 0.600000000000 1622438 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": 1138737, "vin": [ { "gen": { "height": 1138727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99320536eac617352ea4c47007417c68f8d226fde509e60b5f531fd0b739fba7" } } ], "extra": [ 1, 3, 83, 199, 212, 173, 206, 255, 41, 30, 22, 63, 240, 41, 132, 142, 10, 43, 140, 175, 90, 15, 169, 119, 96, 208, 216, 99, 20, 8, 94, 143, 2, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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