Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454956869d3d6951f37a4b081c3f1056df8d83aa6e6a68dd69a4cdb06a71a826

Tx prefix hash: 355669d93fb3f4b2db778115e861fff8ab85d6cc8a969daf99155b8ec91845f0
Tx public key: d513b5a107322df943aee355d3815367dc829649b694a84432e45616ed5f010b
Timestamp: 1700788649 Timestamp [UCT]: 2023-11-24 01:17:29 Age [y:d:h:m:s]: 01:128:08:45:28
Block: 898281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352900 RingCT/type: yes/0
Extra: 01d513b5a107322df943aee355d3815367dc829649b694a84432e45616ed5f010b02110000000733af99f4000000000000000000

1 output(s) for total of 0.648070330000 dcy

stealth address amount amount idx
00: adfa64d509bc01fe41ec0e762e0ce35c2499c104275223435b06856c4d07e592 0.648070330000 1354694 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": 898291, "vin": [ { "gen": { "height": 898281 } } ], "vout": [ { "amount": 648070330, "target": { "key": "adfa64d509bc01fe41ec0e762e0ce35c2499c104275223435b06856c4d07e592" } } ], "extra": [ 1, 213, 19, 181, 161, 7, 50, 45, 249, 67, 174, 227, 85, 211, 129, 83, 103, 220, 130, 150, 73, 182, 148, 168, 68, 50, 228, 86, 22, 237, 95, 1, 11, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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