Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ad1aa8ac049f94410ded1a74c2f0c938d802ce1b2ca56b2eee58cdc1945f06

Tx prefix hash: 8c18853d771f7a0088e11d52a4885ed137c35b89c0df042ee140e2a44f91cb41
Tx public key: 660d1673183eaa0d547c54de57928b6162509fedff4424a15a670727f57cf003
Timestamp: 1728516030 Timestamp [UCT]: 2024-10-09 23:20:30 Age [y:d:h:m:s]: 01:030:01:36:26
Block: 1128156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279859 RingCT/type: yes/0
Extra: 01660d1673183eaa0d547c54de57928b6162509fedff4424a15a670727f57cf00302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e1a34d3d2d8b3f9ad94bd7301ee41e1cf504f1b400667839f2e0cbe6a6cc4d9 0.600000000000 1610973 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": 1128166, "vin": [ { "gen": { "height": 1128156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1a34d3d2d8b3f9ad94bd7301ee41e1cf504f1b400667839f2e0cbe6a6cc4d9" } } ], "extra": [ 1, 102, 13, 22, 115, 24, 62, 170, 13, 84, 124, 84, 222, 87, 146, 139, 97, 98, 80, 159, 237, 255, 68, 36, 161, 90, 103, 7, 39, 245, 124, 240, 3, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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