Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8668120e7836d8ac2df0fa8ed6ded1f0d84725dc9f6a0e68316a50aa4cd910eb

Tx prefix hash: 1796530b0f430243a9394129f6825ebb94233fa4ab3fc68b795c2354d95cff69
Tx public key: 316a3ced43278cd7c025f54f928a5683d914fd81bc32df26220892404a8832a2
Timestamp: 1577046529 Timestamp [UCT]: 2019-12-22 20:28:49 Age [y:d:h:m:s]: 04:321:13:34:33
Block: 29733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118715 RingCT/type: yes/0
Extra: 01316a3ced43278cd7c025f54f928a5683d914fd81bc32df26220892404a8832a2021100000003d81c26c0000000000000000000

1 output(s) for total of 489.196218107000 dcy

stealth address amount amount idx
00: b1c1e529cb01dfc11ba2538a4a5f04ad519af97f142ffbd40d5e2fc97b09f898 489.196218107000 48973 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": 29743, "vin": [ { "gen": { "height": 29733 } } ], "vout": [ { "amount": 489196218107, "target": { "key": "b1c1e529cb01dfc11ba2538a4a5f04ad519af97f142ffbd40d5e2fc97b09f898" } } ], "extra": [ 1, 49, 106, 60, 237, 67, 39, 140, 215, 192, 37, 245, 79, 146, 138, 86, 131, 217, 20, 253, 129, 188, 50, 223, 38, 34, 8, 146, 64, 74, 136, 50, 162, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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