Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6cefea77efe520a8d75e912a922f45b5ae25c619f43797a88787d126186a06

Tx prefix hash: 9503445771055ac379c04122fba15dad92f430aab01f5e46a058ac22af3a0e78
Tx public key: 2175e6fdf912b9f85180c859ce99909e8d0478c55a9dae0bf3973797be7bfcf5
Timestamp: 1681785753 Timestamp [UCT]: 2023-04-18 02:42:33 Age [y:d:h:m:s]: 01:311:23:32:24
Block: 740979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484214 RingCT/type: yes/0
Extra: 012175e6fdf912b9f85180c859ce99909e8d0478c55a9dae0bf3973797be7bfcf5021100000002b3164c24000000000000000000

1 output(s) for total of 2.151935224000 dcy

stealth address amount amount idx
00: ba1a218c7e3a1aaa398e4cd0a9d0b3525a7ee58cf1d683371ae75970dc8f3d94 2.151935224000 1187890 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": 740989, "vin": [ { "gen": { "height": 740979 } } ], "vout": [ { "amount": 2151935224, "target": { "key": "ba1a218c7e3a1aaa398e4cd0a9d0b3525a7ee58cf1d683371ae75970dc8f3d94" } } ], "extra": [ 1, 33, 117, 230, 253, 249, 18, 185, 248, 81, 128, 200, 89, 206, 153, 144, 158, 141, 4, 120, 197, 90, 157, 174, 11, 243, 151, 55, 151, 190, 123, 252, 245, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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