Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ef8e4a85aaf7f3899ba1818bd391291325e51cda460ff8448fa0139f2bd000

Tx prefix hash: 97ada6451b2a4a31f20e32935e93ed34e8a11d61e56e4399cae2141c66973844
Tx public key: 6561e97c6e77071c1f0b4b8b025c8f745364a778978f86c3dd53e4dd985d1822
Timestamp: 1577561791 Timestamp [UCT]: 2019-12-28 19:36:31 Age [y:d:h:m:s]: 05:021:11:08:12
Block: 33763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1165378 RingCT/type: yes/0
Extra: 016561e97c6e77071c1f0b4b8b025c8f745364a778978f86c3dd53e4dd985d1822021100000004d81c26c0000000000000000000

1 output(s) for total of 474.448738359000 dcy

stealth address amount amount idx
00: ffe4d0a03665b806c1e3331b489d8d663a5cb1e1d2bd7b7f5a4abe7372e0d3c2 474.448738359000 56638 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": 33773, "vin": [ { "gen": { "height": 33763 } } ], "vout": [ { "amount": 474448738359, "target": { "key": "ffe4d0a03665b806c1e3331b489d8d663a5cb1e1d2bd7b7f5a4abe7372e0d3c2" } } ], "extra": [ 1, 101, 97, 233, 124, 110, 119, 7, 28, 31, 11, 75, 139, 2, 92, 143, 116, 83, 100, 167, 120, 151, 143, 134, 195, 221, 83, 228, 221, 152, 93, 24, 34, 2, 17, 0, 0, 0, 4, 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