Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6216245d16452d06a79aca5e1f110d6f0b8024ad8657febdb5b51607a122c2

Tx prefix hash: 4b0bbdcc9b2738a8ce6e613405c3b5a34876ad0c268539ef9b593f92db670231
Tx public key: 86be53c8d7ae1e32cf35c0b08b49e449b1e769725331d3cb7b32c9da2b04609b
Timestamp: 1661304347 Timestamp [UCT]: 2022-08-24 01:25:47 Age [y:d:h:m:s]: 02:233:00:09:22
Block: 572446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687780 RingCT/type: yes/0
Extra: 0186be53c8d7ae1e32cf35c0b08b49e449b1e769725331d3cb7b32c9da2b04609b02110000000ae6d27f9c000000000000000000

1 output(s) for total of 7.784825242000 dcy

stealth address amount amount idx
00: 50f11b78296d292e0756127c80db2bbf414306e3f56cbd53a7ebfdeb8752773a 7.784825242000 1005694 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": 572456, "vin": [ { "gen": { "height": 572446 } } ], "vout": [ { "amount": 7784825242, "target": { "key": "50f11b78296d292e0756127c80db2bbf414306e3f56cbd53a7ebfdeb8752773a" } } ], "extra": [ 1, 134, 190, 83, 200, 215, 174, 30, 50, 207, 53, 192, 176, 139, 73, 228, 73, 177, 231, 105, 114, 83, 49, 211, 203, 123, 50, 201, 218, 43, 4, 96, 155, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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