Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1033ebf04ebf7ec87c660bf060d41c306fae9d06d297efdcea0684864fdf8397

Tx prefix hash: 05bd6179eec3e433da35982e1afd13fb05e3d769e9b7cb4e7f338badce88eb63
Tx public key: 1347a7a0a5791f490b65f2cb147ac5d2c2bd52a87ce2e8f9b83c7a3d1e85bb6d
Timestamp: 1734560687 Timestamp [UCT]: 2024-12-18 22:24:47 Age [y:d:h:m:s]: 00:103:12:01:55
Block: 1178183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73727 RingCT/type: yes/0
Extra: 011347a7a0a5791f490b65f2cb147ac5d2c2bd52a87ce2e8f9b83c7a3d1e85bb6d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 499879fb2a09c815c034531f488b6e5639ac00d0bf2f4746d9a750ea38df9ca9 0.600000000000 1664568 of 15

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": 1178193, "vin": [ { "gen": { "height": 1178183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "499879fb2a09c815c034531f488b6e5639ac00d0bf2f4746d9a750ea38df9ca9" } } ], "extra": [ 1, 19, 71, 167, 160, 165, 121, 31, 73, 11, 101, 242, 203, 20, 122, 197, 210, 194, 189, 82, 168, 124, 226, 232, 249, 184, 60, 122, 61, 30, 133, 187, 109, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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