Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50de345d659aaed0f1561c1f8554b45cda57759aacef31db54fdc036305a4bf5

Tx prefix hash: b7f9e92c847cbc7337ddefe80ea13f3c02b157d4a0cc4874e0123a36a77dafd1
Tx public key: f1ec0aa8d8b3fb47ca9be81d0d039f6d77ad450914f95723e6066ff37245eea6
Timestamp: 1694529002 Timestamp [UCT]: 2023-09-12 14:30:02 Age [y:d:h:m:s]: 02:057:10:50:50
Block: 846566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560757 RingCT/type: yes/0
Extra: 01f1ec0aa8d8b3fb47ca9be81d0d039f6d77ad450914f95723e6066ff37245eea602110000000875e3f0e9000000000000000000

1 output(s) for total of 0.961597982000 dcy

stealth address amount amount idx
00: 5b0ba9de51319e862f6fef5fc2dbf66c43f2ee3b34bce2c6cc83f176d84f50f9 0.961597982000 1300034 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": 846576, "vin": [ { "gen": { "height": 846566 } } ], "vout": [ { "amount": 961597982, "target": { "key": "5b0ba9de51319e862f6fef5fc2dbf66c43f2ee3b34bce2c6cc83f176d84f50f9" } } ], "extra": [ 1, 241, 236, 10, 168, 216, 179, 251, 71, 202, 155, 232, 29, 13, 3, 159, 109, 119, 173, 69, 9, 20, 249, 87, 35, 230, 6, 111, 243, 114, 69, 238, 166, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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