Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc35e3bf3951dd31810c53f267f3bc632c53f3b830fe95bd0d11763ad68847d

Tx prefix hash: 5fb38b84f85e49743f450a7155e4de5f4fa22ca4938332d924cd0e9e89813922
Tx public key: 739c4d22ee1b6d4e926dd1927ffcc5dbbc86757d1a2886b81e931f2ba55daf73
Timestamp: 1705709607 Timestamp [UCT]: 2024-01-20 00:13:27 Age [y:d:h:m:s]: 01:301:02:14:43
Block: 939055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474024 RingCT/type: yes/0
Extra: 01739c4d22ee1b6d4e926dd1927ffcc5dbbc86757d1a2886b81e931f2ba55daf730211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482172986867eb0a9fdd4af4787d3f8a51d43b1fef7b3a4fd31db7ffabcb4ce5 0.600000000000 1397139 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": 939065, "vin": [ { "gen": { "height": 939055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482172986867eb0a9fdd4af4787d3f8a51d43b1fef7b3a4fd31db7ffabcb4ce5" } } ], "extra": [ 1, 115, 156, 77, 34, 238, 27, 109, 78, 146, 109, 209, 146, 127, 252, 197, 219, 188, 134, 117, 125, 26, 40, 134, 184, 30, 147, 31, 43, 165, 93, 175, 115, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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