Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d13cb35ddd5f79b33dbf17add6da634a34f57ec5fb4537dea111662a2f9c989

Tx prefix hash: 86654395b19d3d79797d0fe2bdd24d0107044b5b56c36dfc86b6e5895621f266
Tx public key: aec5071cda32b501065b17e6304ea96f720afbaa96b4af25e6c2448ca0c1fab9
Timestamp: 1702107145 Timestamp [UCT]: 2023-12-09 07:32:25 Age [y:d:h:m:s]: 01:334:00:07:41
Block: 909207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497581 RingCT/type: yes/0
Extra: 01aec5071cda32b501065b17e6304ea96f720afbaa96b4af25e6c2448ca0c1fab902110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02382610cd5cace0a1e7a8d6cd8538be13067c8568424cb63c820f4ba45e9254 0.600000000000 1366278 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": 909217, "vin": [ { "gen": { "height": 909207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02382610cd5cace0a1e7a8d6cd8538be13067c8568424cb63c820f4ba45e9254" } } ], "extra": [ 1, 174, 197, 7, 28, 218, 50, 181, 1, 6, 91, 23, 230, 48, 78, 169, 111, 114, 10, 251, 170, 150, 180, 175, 37, 230, 194, 68, 140, 160, 193, 250, 185, 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