Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c1464cadd955cd26bb387f0a4a2624d15a069cc17cc2e64b9608cb00618e43f

Tx prefix hash: f5a99fddb8876fb8170b2fe23ffb0582d619cc19edda331eed990a8eaf35e10f
Tx public key: 85e5cd8e0ad4b4726a43a6f51a92610b9fa2ec916611ccc35e0063e520cbe966
Timestamp: 1732519415 Timestamp [UCT]: 2024-11-25 07:23:35 Age [y:d:h:m:s]: 00:346:06:22:01
Block: 1161247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244985 RingCT/type: yes/0
Extra: 0185e5cd8e0ad4b4726a43a6f51a92610b9fa2ec916611ccc35e0063e520cbe966021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f46b7b3f70df2cabc0196ea9c0a0a6e128970d8a839af6259a20104829001a 0.600000000000 1646898 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": 1161257, "vin": [ { "gen": { "height": 1161247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f46b7b3f70df2cabc0196ea9c0a0a6e128970d8a839af6259a20104829001a" } } ], "extra": [ 1, 133, 229, 205, 142, 10, 212, 180, 114, 106, 67, 166, 245, 26, 146, 97, 11, 159, 162, 236, 145, 102, 17, 204, 195, 94, 0, 99, 229, 32, 203, 233, 102, 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