Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b493203df7bd44e1dc2045920dd16e898fba53e83f1588c5f617830f2f5eb0cb

Tx prefix hash: e6287aa8107bb5a5906487520dc8e75e3be764ad9ee18f4604855de58546cc8a
Tx public key: 7dfe9a905fe60fb055bfd24110843011138ac660b325f085647c0b04e05b3395
Timestamp: 1697387883 Timestamp [UCT]: 2023-10-15 16:38:03 Age [y:d:h:m:s]: 01:170:05:21:31
Block: 870296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382671 RingCT/type: yes/0
Extra: 017dfe9a905fe60fb055bfd24110843011138ac660b325f085647c0b04e05b3395021100000002e08532b6000000000000000000

1 output(s) for total of 0.802320893000 dcy

stealth address amount amount idx
00: bf52168f5e2e4a19f0f0af88a90ed0a36ffcc0edb3b5f77c2ceadf34de11d4ab 0.802320893000 1325175 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": 870306, "vin": [ { "gen": { "height": 870296 } } ], "vout": [ { "amount": 802320893, "target": { "key": "bf52168f5e2e4a19f0f0af88a90ed0a36ffcc0edb3b5f77c2ceadf34de11d4ab" } } ], "extra": [ 1, 125, 254, 154, 144, 95, 230, 15, 176, 85, 191, 210, 65, 16, 132, 48, 17, 19, 138, 198, 96, 179, 37, 240, 133, 100, 124, 11, 4, 224, 91, 51, 149, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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