Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b94af54950b9d0215bfe3c66d23482695568494093ec80396d935c6abbfea8f

Tx prefix hash: 5534e87e0afb3c49edb503eb889f2d7f1d49254b0ab5348a64d8ad4d45aad5d6
Tx public key: f8d3a59ff532c22e2154bd79ced022f24e0976e81246204cfcf23aa0ff6aec39
Timestamp: 1737812007 Timestamp [UCT]: 2025-01-25 13:33:27 Age [y:d:h:m:s]: 00:048:11:12:00
Block: 1205028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34459 RingCT/type: yes/0
Extra: 01f8d3a59ff532c22e2154bd79ced022f24e0976e81246204cfcf23aa0ff6aec39021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f7c42eb87a1a2322ea6b1d54d440c0c18ff8ef5ffcabf43b9b46c16a44ed6c6 0.600000000000 1691725 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": 1205038, "vin": [ { "gen": { "height": 1205028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7c42eb87a1a2322ea6b1d54d440c0c18ff8ef5ffcabf43b9b46c16a44ed6c6" } } ], "extra": [ 1, 248, 211, 165, 159, 245, 50, 194, 46, 33, 84, 189, 121, 206, 208, 34, 242, 78, 9, 118, 232, 18, 70, 32, 76, 252, 242, 58, 160, 255, 106, 236, 57, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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