Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 794beb566707d1ad396df3b5da45c221a1154a8517e36d6d0a9a0bca78dee823

Tx prefix hash: 0c57601cbfe80861bc250bb69167c41f4a14ca934c6ce3e4c748a09a9085d996
Tx public key: c677158a1c3130a01416e78a991cebec0e60fd813fec6b5ae60703cb5f2210d7
Timestamp: 1674806739 Timestamp [UCT]: 2023-01-27 08:05:39 Age [y:d:h:m:s]: 02:284:08:24:36
Block: 683756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722565 RingCT/type: yes/0
Extra: 01c677158a1c3130a01416e78a991cebec0e60fd813fec6b5ae60703cb5f2210d70211000000035029cbac000000000000000000

1 output(s) for total of 3.329909791000 dcy

stealth address amount amount idx
00: 66ac48f5177a464f288d41b22e648bb6155d7b1730009a30d06e6f6a12150aaf 3.329909791000 1125955 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": 683766, "vin": [ { "gen": { "height": 683756 } } ], "vout": [ { "amount": 3329909791, "target": { "key": "66ac48f5177a464f288d41b22e648bb6155d7b1730009a30d06e6f6a12150aaf" } } ], "extra": [ 1, 198, 119, 21, 138, 28, 49, 48, 160, 20, 22, 231, 138, 153, 28, 235, 236, 14, 96, 253, 129, 63, 236, 107, 90, 230, 7, 3, 203, 95, 34, 16, 215, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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