Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e6d8e6f83dd41ebba34470e26103eba81b5f499c943d9f2cd258c2763fc646b

Tx prefix hash: 04c4f6fd50c7eb532d0e0c4c28102d30f65ea8a11dd1bb81bc2ac333846c03ba
Tx public key: cf2611ec37d0aedb0e501f1a37fe0975b53defa2e64e6663ddfd6426c2c6fff9
Timestamp: 1629043861 Timestamp [UCT]: 2021-08-15 16:11:01 Age [y:d:h:m:s]: 03:134:16:29:38
Block: 314712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 869467 RingCT/type: yes/0
Extra: 01cf2611ec37d0aedb0e501f1a37fe0975b53defa2e64e6663ddfd6426c2c6fff902110000002501f1e57f000000000000000000

1 output(s) for total of 55.619741971000 dcy

stealth address amount amount idx
00: 5caf2460f74a2a5d1c52185d828ee3a8f4f59386561de739781be56a1d9335bf 55.619741971000 655109 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": 314722, "vin": [ { "gen": { "height": 314712 } } ], "vout": [ { "amount": 55619741971, "target": { "key": "5caf2460f74a2a5d1c52185d828ee3a8f4f59386561de739781be56a1d9335bf" } } ], "extra": [ 1, 207, 38, 17, 236, 55, 208, 174, 219, 14, 80, 31, 26, 55, 254, 9, 117, 181, 61, 239, 162, 230, 78, 102, 99, 221, 253, 100, 38, 194, 198, 255, 249, 2, 17, 0, 0, 0, 37, 1, 241, 229, 127, 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