Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e87739ebcc8d3680140576d808e0df2d3cbc819b6677867cd85ba4e9110cd88

Tx prefix hash: c68408cb3e7535bb53592388458c215fc1b736f9db04851807127fd4441f9f8d
Tx public key: dfa08a63f7bc65d2ac59503c4127e7d1a0fa9b004b9bc7daa4dce064944bdabf
Timestamp: 1695557077 Timestamp [UCT]: 2023-09-24 12:04:37 Age [y:d:h:m:s]: 01:257:19:11:17
Block: 855105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445366 RingCT/type: yes/0
Extra: 01dfa08a63f7bc65d2ac59503c4127e7d1a0fa9b004b9bc7daa4dce064944bdabf021100000002faf35c9c000000000000000000

1 output(s) for total of 0.900911671000 dcy

stealth address amount amount idx
00: 6b261a471c2a4713ae4ec883fe9b2b779d3ab9d59f5c5b7f378405c032b7af4e 0.900911671000 1309109 of 0

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": 855115, "vin": [ { "gen": { "height": 855105 } } ], "vout": [ { "amount": 900911671, "target": { "key": "6b261a471c2a4713ae4ec883fe9b2b779d3ab9d59f5c5b7f378405c032b7af4e" } } ], "extra": [ 1, 223, 160, 138, 99, 247, 188, 101, 210, 172, 89, 80, 60, 65, 39, 231, 209, 160, 250, 155, 0, 75, 155, 199, 218, 164, 220, 224, 100, 148, 75, 218, 191, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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