Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f66abb87534b126c923b19f1da32613954d7ae842411dd1730adccf60dd3101

Tx prefix hash: af59389c47eecb10f213c30101717c0fd262480d56608e26a7f1e84cedcd1e8a
Tx public key: e47cdd321ff8147ea947b96d40f3f7da9076802caa2d9458eab641e75b3dc36b
Timestamp: 1724320875 Timestamp [UCT]: 2024-08-22 10:01:15 Age [y:d:h:m:s]: 00:225:02:34:48
Block: 1093390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160737 RingCT/type: yes/0
Extra: 01e47cdd321ff8147ea947b96d40f3f7da9076802caa2d9458eab641e75b3dc36b021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f90f5b01ac9d606888be9add4210a8a3078c06e61c820ed69c5d7c54e99c07e 0.600000000000 1568325 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": 1093400, "vin": [ { "gen": { "height": 1093390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f90f5b01ac9d606888be9add4210a8a3078c06e61c820ed69c5d7c54e99c07e" } } ], "extra": [ 1, 228, 124, 221, 50, 31, 248, 20, 126, 169, 71, 185, 109, 64, 243, 247, 218, 144, 118, 128, 44, 170, 45, 148, 88, 234, 182, 65, 231, 91, 61, 195, 107, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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