Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b3da3dd8cf896b84ccb755ac7b68db6505ae39bd0a3975df46798e4dffc737a

Tx prefix hash: b7a5346eb5d339dd23b3e7350d931f4fe05b3b6defea49082e7d86c33f8f323f
Tx public key: 3111b27083d4e53a8ce46503a8db701a978d72369ffe1824efe0606c9bde434f
Timestamp: 1718530257 Timestamp [UCT]: 2024-06-16 09:30:57 Age [y:d:h:m:s]: 00:271:06:06:20
Block: 1045384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193833 RingCT/type: yes/0
Extra: 013111b27083d4e53a8ce46503a8db701a978d72369ffe1824efe0606c9bde434f02110000000252d47e94000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 7c934baaecbb8f8168b3db0d87fd1d2a5dea131d25cb65ca1e331bf0b0459739 0.600060000000 1514941 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": 1045394, "vin": [ { "gen": { "height": 1045384 } } ], "vout": [ { "amount": 600060000, "target": { "key": "7c934baaecbb8f8168b3db0d87fd1d2a5dea131d25cb65ca1e331bf0b0459739" } } ], "extra": [ 1, 49, 17, 178, 112, 131, 212, 229, 58, 140, 228, 101, 3, 168, 219, 112, 26, 151, 141, 114, 54, 159, 254, 24, 36, 239, 224, 96, 108, 155, 222, 67, 79, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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