Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75313ec338d84c9ab8958ecf87ad9df3ba54ca885b4bd6222e78a7ce7c1fab85

Tx prefix hash: 57412b57b675419e47af8d8a8f018a5ed7e8483f2a217f82c0fa16777d7addee
Tx public key: df70047387e1c71c5b81264676df48d60e00d6d48f6a87f4c75385ae6e104842
Timestamp: 1759498993 Timestamp [UCT]: 2025-10-03 13:43:13 Age [y:d:h:m:s]: 00:004:09:04:36
Block: 1381906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3123 RingCT/type: yes/0
Extra: 01df70047387e1c71c5b81264676df48d60e00d6d48f6a87f4c75385ae6e1048420211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 196df40f9f91b92c06d66c248d2173c3b13cddc7656ee85faa0ed61314f171a9 0.600000000000 1870037 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": 1381916, "vin": [ { "gen": { "height": 1381906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "196df40f9f91b92c06d66c248d2173c3b13cddc7656ee85faa0ed61314f171a9" } } ], "extra": [ 1, 223, 112, 4, 115, 135, 225, 199, 28, 91, 129, 38, 70, 118, 223, 72, 214, 14, 0, 214, 212, 143, 106, 135, 244, 199, 83, 133, 174, 110, 16, 72, 66, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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