Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b761d47ab231a326ee00cc216d98041d4979beb0914c25dad4ac3905738f96eb

Tx prefix hash: 6e1a18761ddc4e1e718a89795d4bf36433037ceea978bbf921c11d69db212d41
Tx public key: 8f60c4c38f346281524e5052393aa438f6d9470a08d5aa4f468690ff5ac637aa
Timestamp: 1711362892 Timestamp [UCT]: 2024-03-25 10:34:52 Age [y:d:h:m:s]: 01:223:19:40:50
Block: 985973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418627 RingCT/type: yes/0
Extra: 018f60c4c38f346281524e5052393aa438f6d9470a08d5aa4f468690ff5ac637aa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76af19638f4f807de45d6b3c487af60a1e4178eaefb7b009903a28f002096b36 0.600000000000 1446194 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": 985983, "vin": [ { "gen": { "height": 985973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76af19638f4f807de45d6b3c487af60a1e4178eaefb7b009903a28f002096b36" } } ], "extra": [ 1, 143, 96, 196, 195, 143, 52, 98, 129, 82, 78, 80, 82, 57, 58, 164, 56, 246, 217, 71, 10, 8, 213, 170, 79, 70, 134, 144, 255, 90, 198, 55, 170, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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