Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4428b9f089530725c7ac8ba6d30cf495785af97c9539c87cf6eee39d04bf9481

Tx prefix hash: 96622bd4df595cc4f47237853d688de892fe98fd17642e3d352c76eec3180e74
Tx public key: 4a6d581f4b8312a8947930d3ad6b41c04f1430ee5335e4abca9c6dc78f6f6a87
Timestamp: 1721492669 Timestamp [UCT]: 2024-07-20 16:24:29 Age [y:d:h:m:s]: 00:326:20:03:00
Block: 1069925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233518 RingCT/type: yes/0
Extra: 014a6d581f4b8312a8947930d3ad6b41c04f1430ee5335e4abca9c6dc78f6f6a87021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef3675f7addbf74ba6a8691a59450d1a27a486fdc7e607195ebf66f8c4250042 0.600000000000 1541550 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": 1069935, "vin": [ { "gen": { "height": 1069925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef3675f7addbf74ba6a8691a59450d1a27a486fdc7e607195ebf66f8c4250042" } } ], "extra": [ 1, 74, 109, 88, 31, 75, 131, 18, 168, 148, 121, 48, 211, 173, 107, 65, 192, 79, 20, 48, 238, 83, 53, 228, 171, 202, 156, 109, 199, 143, 111, 106, 135, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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