Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe36fca38c7f04e343b3c84919e494480d57138469e8281bc8eec28f3bfde70e

Tx prefix hash: 7440402119ea475764261f6436e22ac5cc0717a078bf283571013c4204731909
Tx public key: e1de6289e9f0057e3c3d4936dd28e53b5c3d27d4546c60c40dc6a92a943b1415
Timestamp: 1726687412 Timestamp [UCT]: 2024-09-18 19:23:32 Age [y:d:h:m:s]: 00:066:23:21:12
Block: 1113002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47869 RingCT/type: yes/0
Extra: 01e1de6289e9f0057e3c3d4936dd28e53b5c3d27d4546c60c40dc6a92a943b141502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59ce23d6a73873c7a9f39ad7c87371a1bcaaa488754108e64e7cf896ea3f405d 0.600000000000 1592521 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": 1113012, "vin": [ { "gen": { "height": 1113002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59ce23d6a73873c7a9f39ad7c87371a1bcaaa488754108e64e7cf896ea3f405d" } } ], "extra": [ 1, 225, 222, 98, 137, 233, 240, 5, 126, 60, 61, 73, 54, 221, 40, 229, 59, 92, 61, 39, 212, 84, 108, 96, 196, 13, 198, 169, 42, 148, 59, 20, 21, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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