Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 348e0ef0be21c55fabbec7ac6e1f9b16c4217f14342457cf3a47ad36ab430ad6

Tx prefix hash: dc4f67f4442eba5666352c8f3e3d749cd8cf04099efae8a22987b2748a4bdec0
Tx public key: 5181d7a8e572da475e4c7bdcb0bc81f95b4985c554f47f3267a61c819eed2f04
Timestamp: 1730672436 Timestamp [UCT]: 2024-11-03 22:20:36 Age [y:d:h:m:s]: 00:020:05:29:34
Block: 1145949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14481 RingCT/type: yes/0
Extra: 015181d7a8e572da475e4c7bdcb0bc81f95b4985c554f47f3267a61c819eed2f040211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f28495720537a0bd39800a86e67ff72a78147eab43ad81141b03bb8a4d8693f1 0.600000000000 1630482 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": 1145959, "vin": [ { "gen": { "height": 1145949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f28495720537a0bd39800a86e67ff72a78147eab43ad81141b03bb8a4d8693f1" } } ], "extra": [ 1, 81, 129, 215, 168, 229, 114, 218, 71, 94, 76, 123, 220, 176, 188, 129, 249, 91, 73, 133, 197, 84, 244, 127, 50, 103, 166, 28, 129, 158, 237, 47, 4, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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