Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f53613949f19e940070e1a546fa29f127e078466b2416d0ba32b23d197b218a

Tx prefix hash: 5209c7fc96ce56d39a99708902ce124901ef2fd8a0a921e2a3da994180ad8fe5
Tx public key: b93c3c458e13ca628a52ea04f6f8f3f9578e9cbfea8455d045d6b3963812909e
Timestamp: 1703495510 Timestamp [UCT]: 2023-12-25 09:11:50 Age [y:d:h:m:s]: 01:317:12:27:08
Block: 920736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485742 RingCT/type: yes/0
Extra: 01b93c3c458e13ca628a52ea04f6f8f3f9578e9cbfea8455d045d6b3963812909e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 450f0c2063477327330308b4e58b594f051527ec2be02aaabbc894920073abc4 0.600000000000 1378418 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": 920746, "vin": [ { "gen": { "height": 920736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "450f0c2063477327330308b4e58b594f051527ec2be02aaabbc894920073abc4" } } ], "extra": [ 1, 185, 60, 60, 69, 142, 19, 202, 98, 138, 82, 234, 4, 246, 248, 243, 249, 87, 142, 156, 191, 234, 132, 85, 208, 69, 214, 179, 150, 56, 18, 144, 158, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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