Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47eb128d3f4ce40044bb1764f24fe453b3d3e7485670f1aceda744ebdc278100

Tx prefix hash: 6adef3f16c490d9b200f17eb8e5f770171d97bd655b29b93098935849a2b1c21
Tx public key: e58b24a3fbc4d830a2e00cd3698e1118a84351a1f928d36e4e5c5830a5293486
Timestamp: 1717410095 Timestamp [UCT]: 2024-06-03 10:21:35 Age [y:d:h:m:s]: 00:182:01:34:43
Block: 1036096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130299 RingCT/type: yes/0
Extra: 01e58b24a3fbc4d830a2e00cd3698e1118a84351a1f928d36e4e5c5830a52934860211000000024385362a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a700d39c1a3e84ea49e164a3f8e0857b0695f04c0b4d49709063766b274ad2f5 0.600000000000 1504621 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": 1036106, "vin": [ { "gen": { "height": 1036096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a700d39c1a3e84ea49e164a3f8e0857b0695f04c0b4d49709063766b274ad2f5" } } ], "extra": [ 1, 229, 139, 36, 163, 251, 196, 216, 48, 162, 224, 12, 211, 105, 142, 17, 24, 168, 67, 81, 161, 249, 40, 211, 110, 78, 92, 88, 48, 165, 41, 52, 134, 2, 17, 0, 0, 0, 2, 67, 133, 54, 42, 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