Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19c023650a280b9f0b0c0e604ce44dc81e6f71b397b68adaaf3ac298600ce83

Tx prefix hash: 8db56ef4e150c10e893732d6b518eca3e4791b2a1cf5f93be8c2e1cdbc9b443d
Tx public key: ec5b2bc07d7a8a017c0ec675a9f790c33bdb215b0b3b31f563324c6c6643e978
Timestamp: 1698544206 Timestamp [UCT]: 2023-10-29 01:50:06 Age [y:d:h:m:s]: 01:142:16:15:08
Block: 879890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362975 RingCT/type: yes/0
Extra: 01ec5b2bc07d7a8a017c0ec675a9f790c33bdb215b0b3b31f563324c6c6643e97802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.745691484000 dcy

stealth address amount amount idx
00: 29f16a9e76e8374208c1093a19330165b9be5465d8e811d83651ee804bddebc9 0.745691484000 1335430 of 0

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": 879900, "vin": [ { "gen": { "height": 879890 } } ], "vout": [ { "amount": 745691484, "target": { "key": "29f16a9e76e8374208c1093a19330165b9be5465d8e811d83651ee804bddebc9" } } ], "extra": [ 1, 236, 91, 43, 192, 125, 122, 138, 1, 124, 14, 198, 117, 169, 247, 144, 195, 59, 219, 33, 91, 11, 59, 49, 245, 99, 50, 76, 108, 102, 67, 233, 120, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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