Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e6ac1a555a86ac53e17877fe0b0171c3449cac1cb4a90b454784021234c443

Tx prefix hash: b51c790c967608bb83e6453c936b86b2c043c95958e3c162eff043e59acb73b6
Tx public key: fbb89e70aa7bf89602903b62647a7e5fd4d3237ef9f0f4f782fcd0552282ee0d
Timestamp: 1726391536 Timestamp [UCT]: 2024-09-15 09:12:16 Age [y:d:h:m:s]: 00:249:18:36:35
Block: 1110547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178378 RingCT/type: yes/0
Extra: 01fbb89e70aa7bf89602903b62647a7e5fd4d3237ef9f0f4f782fcd0552282ee0d02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc0816b8d8fca62d7f4f73baaba5cb81129a7ad60c4c5a2e0ddf111ace2f494 0.600000000000 1589190 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": 1110557, "vin": [ { "gen": { "height": 1110547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc0816b8d8fca62d7f4f73baaba5cb81129a7ad60c4c5a2e0ddf111ace2f494" } } ], "extra": [ 1, 251, 184, 158, 112, 170, 123, 248, 150, 2, 144, 59, 98, 100, 122, 126, 95, 212, 211, 35, 126, 249, 240, 244, 247, 130, 252, 208, 85, 34, 130, 238, 13, 2, 17, 0, 0, 0, 10, 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