Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 788b9de0b541b393ea5997687d8fd9b08d5ac992136b3d0f4fa01a88d6e3d520

Tx prefix hash: 7ad09e297d6008992e1bb8ba168dbde3ca54788f5546ec432ee79196553e7aeb
Tx public key: 8761736333e4aee85afcbc7daf1a059837accc3dc5498a6916222065dc4d8cd0
Timestamp: 1708419316 Timestamp [UCT]: 2024-02-20 08:55:16 Age [y:d:h:m:s]: 01:117:09:13:04
Block: 961548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344850 RingCT/type: yes/0
Extra: 018761736333e4aee85afcbc7daf1a059837accc3dc5498a6916222065dc4d8cd002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70bbf09dbb9886f07d4db5adc07faff930cbfa376a5b8217a23df120ffd1a7d4 0.600000000000 1421159 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": 961558, "vin": [ { "gen": { "height": 961548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70bbf09dbb9886f07d4db5adc07faff930cbfa376a5b8217a23df120ffd1a7d4" } } ], "extra": [ 1, 135, 97, 115, 99, 51, 228, 174, 232, 90, 252, 188, 125, 175, 26, 5, 152, 55, 172, 204, 61, 197, 73, 138, 105, 22, 34, 32, 101, 220, 77, 140, 208, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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