Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 782e52d62b78fb9843a155626f342e19fec92a79de1c7c4735094adc6cf8b93c

Tx prefix hash: 310827b2c058902b7be0cdc78dd58932d520f4f3c098c1d1aa5dda351a448cdb
Tx public key: 718ec18f9753875e3d92d934b4665e01e108f00660b9ae873e3f2ab6be447556
Timestamp: 1711500358 Timestamp [UCT]: 2024-03-27 00:45:58 Age [y:d:h:m:s]: 01:006:02:05:35
Block: 987115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265275 RingCT/type: yes/0
Extra: 01718ec18f9753875e3d92d934b4665e01e108f00660b9ae873e3f2ab6be44755602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14e94aefac669664ef24bc3c1fa271554d3ab9d7f473d2ba5cfffccc912df926 0.600000000000 1447356 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": 987125, "vin": [ { "gen": { "height": 987115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14e94aefac669664ef24bc3c1fa271554d3ab9d7f473d2ba5cfffccc912df926" } } ], "extra": [ 1, 113, 142, 193, 143, 151, 83, 135, 94, 61, 146, 217, 52, 180, 102, 94, 1, 225, 8, 240, 6, 96, 185, 174, 135, 62, 63, 42, 182, 190, 68, 117, 86, 2, 17, 0, 0, 0, 6, 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