Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b8db7ec9f55a7042ff218048b93d1f63fcd7ba229593f0d0bca1ddb68a696bf

Tx prefix hash: 641dd3d20345d2082dd9a677fceedfa5a64ac1a7a1c47fba53c5bafec1f823aa
Tx public key: a3d06e1d14d641cb7845429210109abf396187a5e83925ce922bc3939f5b8c10
Timestamp: 1723416139 Timestamp [UCT]: 2024-08-11 22:42:19 Age [y:d:h:m:s]: 00:309:20:42:39
Block: 1085875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221275 RingCT/type: yes/0
Extra: 01a3d06e1d14d641cb7845429210109abf396187a5e83925ce922bc3939f5b8c10021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d36944677c026507d67ea03ac0f69761e25f2ce25b11b82f0dc554db400f026 0.600000000000 1560466 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": 1085885, "vin": [ { "gen": { "height": 1085875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d36944677c026507d67ea03ac0f69761e25f2ce25b11b82f0dc554db400f026" } } ], "extra": [ 1, 163, 208, 110, 29, 20, 214, 65, 203, 120, 69, 66, 146, 16, 16, 154, 191, 57, 97, 135, 165, 232, 57, 37, 206, 146, 43, 195, 147, 159, 91, 140, 16, 2, 17, 0, 0, 0, 1, 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