Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1d227ae0c9d54817706b9f1b9e79c26b256e4a62791115126e4ee73ff44ab4

Tx prefix hash: 21ee4155cb09089256ab24c43a4b84281966b8ef990c1f3aa8bb522d53f2e3b0
Tx public key: 35e9e912eeb49ce62924759ae9d2d97964f1b9351580372381ddde7ab1f357b9
Timestamp: 1673932989 Timestamp [UCT]: 2023-01-17 05:23:09 Age [y:d:h:m:s]: 02:001:19:33:14
Block: 676495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523192 RingCT/type: yes/0
Extra: 0135e9e912eeb49ce62924759ae9d2d97964f1b9351580372381ddde7ab1f357b90211000000018b7b6602000000000000000000

1 output(s) for total of 3.519582797000 dcy

stealth address amount amount idx
00: b7a1acbca24c32dba695b8bbe2bdfad7478eafb72b89d3970a6ebe808b9e3b52 3.519582797000 1118212 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": 676505, "vin": [ { "gen": { "height": 676495 } } ], "vout": [ { "amount": 3519582797, "target": { "key": "b7a1acbca24c32dba695b8bbe2bdfad7478eafb72b89d3970a6ebe808b9e3b52" } } ], "extra": [ 1, 53, 233, 233, 18, 238, 180, 156, 230, 41, 36, 117, 154, 233, 210, 217, 121, 100, 241, 185, 53, 21, 128, 55, 35, 129, 221, 222, 122, 177, 243, 87, 185, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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