Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38a8e603f19993fc921d178350d1dbc705a5b8c468a0b3cc46731815b24510d0

Tx prefix hash: ddaaa763956ec91f1f89d20ab77a8c75dd7573eb5109fdd7c7d2ac5d192803a7
Tx public key: 3b9141e9e313f42d28b8fe724c8bed9dcfd9bd7b31d9225795197b54e59eb15a
Timestamp: 1715853015 Timestamp [UCT]: 2024-05-16 09:50:15 Age [y:d:h:m:s]: 00:352:02:57:24
Block: 1023176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251701 RingCT/type: yes/0
Extra: 013b9141e9e313f42d28b8fe724c8bed9dcfd9bd7b31d9225795197b54e59eb15a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e183551410daa5fb736f072c02f5eec77855b2f4aca3c20cd08ab4dbd1995bc0 0.600000000000 1487993 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": 1023186, "vin": [ { "gen": { "height": 1023176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e183551410daa5fb736f072c02f5eec77855b2f4aca3c20cd08ab4dbd1995bc0" } } ], "extra": [ 1, 59, 145, 65, 233, 227, 19, 244, 45, 40, 184, 254, 114, 76, 139, 237, 157, 207, 217, 189, 123, 49, 217, 34, 87, 149, 25, 123, 84, 229, 158, 177, 90, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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