Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51bb66bfa1cf9c4dfc69fac79ec62b24c4dd2f80e9bb48fe3dfd55d6169e7c89

Tx prefix hash: 9e7fe5a28c9389517b11c2abc1c3c7211cf43dfe935ff8109d60ba8214b8be0f
Tx public key: aa94be60c520527312a596a5464cc5e060a14447c5f853f28f17fe52b4164f57
Timestamp: 1710356001 Timestamp [UCT]: 2024-03-13 18:53:21 Age [y:d:h:m:s]: 01:267:06:04:29
Block: 977619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449725 RingCT/type: yes/0
Extra: 01aa94be60c520527312a596a5464cc5e060a14447c5f853f28f17fe52b4164f5702110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b641ba7c4d0313e7396291ff95d9ddcecbf36a06b85b7815c532c3b426a9170 0.600000000000 1437622 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": 977629, "vin": [ { "gen": { "height": 977619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b641ba7c4d0313e7396291ff95d9ddcecbf36a06b85b7815c532c3b426a9170" } } ], "extra": [ 1, 170, 148, 190, 96, 197, 32, 82, 115, 18, 165, 150, 165, 70, 76, 197, 224, 96, 161, 68, 71, 197, 248, 83, 242, 143, 23, 254, 82, 180, 22, 79, 87, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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