Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0505932d4562c5fc825ed7636a8498e15f4ec49f63844f2ad35bc9c264a83e3d

Tx prefix hash: 3de47974f09cf4073b0c018a6f36c3476d4fbf7ae3488dc3967387b4f3ed8c6c
Tx public key: 20c90cc8c4d8860dd9b12d75db7668a922fd7dde9188b7869bae7d345b1a8685
Timestamp: 1700714554 Timestamp [UCT]: 2023-11-23 04:42:34 Age [y:d:h:m:s]: 01:098:18:23:58
Block: 897674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331721 RingCT/type: yes/0
Extra: 0120c90cc8c4d8860dd9b12d75db7668a922fd7dde9188b7869bae7d345b1a86850211000000044b8f5122000000000000000000

1 output(s) for total of 0.651108542000 dcy

stealth address amount amount idx
00: 2b5b0b6b9e9bc2a8eea96f6f8d437e7b5799cacecfa8c4b2e7d5bfd6e12107cb 0.651108542000 1354059 of 0

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": 897684, "vin": [ { "gen": { "height": 897674 } } ], "vout": [ { "amount": 651108542, "target": { "key": "2b5b0b6b9e9bc2a8eea96f6f8d437e7b5799cacecfa8c4b2e7d5bfd6e12107cb" } } ], "extra": [ 1, 32, 201, 12, 200, 196, 216, 134, 13, 217, 177, 45, 117, 219, 118, 104, 169, 34, 253, 125, 222, 145, 136, 183, 134, 155, 174, 125, 52, 91, 26, 134, 133, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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