Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92d04d3e2fb17511853954f81009c32ab0805503a632d009a06271ba4c513eaf

Tx prefix hash: ccec4848685769304c441fb36b4549c7bd571e2bcc8bd3fb3fc897949e9942b7
Tx public key: 28f06c618e9c2f09cd4ebf2e37584b3f8a2ca753403f3c49234171af98bcdce8
Timestamp: 1645816281 Timestamp [UCT]: 2022-02-25 19:11:21 Age [y:d:h:m:s]: 02:350:19:32:52
Block: 446393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769890 RingCT/type: yes/0
Extra: 0128f06c618e9c2f09cd4ebf2e37584b3f8a2ca753403f3c49234171af98bcdce8021100000010cb8520c2000000000000000000

1 output(s) for total of 20.366432797000 dcy

stealth address amount amount idx
00: b7f84c79e9d7d9a629b48ebb0edf0cbc5f0e1945bb8193017825cbab4cba2387 20.366432797000 860270 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": 446403, "vin": [ { "gen": { "height": 446393 } } ], "vout": [ { "amount": 20366432797, "target": { "key": "b7f84c79e9d7d9a629b48ebb0edf0cbc5f0e1945bb8193017825cbab4cba2387" } } ], "extra": [ 1, 40, 240, 108, 97, 142, 156, 47, 9, 205, 78, 191, 46, 55, 88, 75, 63, 138, 44, 167, 83, 64, 63, 60, 73, 35, 65, 113, 175, 152, 188, 220, 232, 2, 17, 0, 0, 0, 16, 203, 133, 32, 194, 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