Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9358d373f1baef8b2005481483fa73650f291cfb30dc36a26d27aac5be6244b

Tx prefix hash: be63e8dc1b1860d2eee796645b0ea327c5e8185392f64853550f6e0fef76c9a8
Tx public key: 0f90587115ea8c3c34b3bab06e3fc124c3bfac1d174193a323259c8b639527c7
Timestamp: 1738212921 Timestamp [UCT]: 2025-01-30 04:55:21 Age [y:d:h:m:s]: 00:137:12:16:05
Block: 1208127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98255 RingCT/type: yes/0
Extra: 010f90587115ea8c3c34b3bab06e3fc124c3bfac1d174193a323259c8b639527c7021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1029c8ee01ed558c589a33c7657c8f54e1ffb42b9db073ea7551e90ed9c66a2 0.600000000000 1694856 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": 1208137, "vin": [ { "gen": { "height": 1208127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1029c8ee01ed558c589a33c7657c8f54e1ffb42b9db073ea7551e90ed9c66a2" } } ], "extra": [ 1, 15, 144, 88, 113, 21, 234, 140, 60, 52, 179, 186, 176, 110, 63, 193, 36, 195, 191, 172, 29, 23, 65, 147, 163, 35, 37, 156, 139, 99, 149, 39, 199, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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