Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a046de0cf003fc60aae0482839b53229b211afdf3ad1d02b096fd93ad8b5975

Tx prefix hash: 3a3b175631446af61aff789ea251cba51515dd28d520dfdef08885f24f14cc5e
Tx public key: 4e6cf1f4e15fe45c9f700f08d0bb673b2b66d80ecd73bf3f9730aadef0af67b7
Timestamp: 1729214100 Timestamp [UCT]: 2024-10-18 01:15:00 Age [y:d:h:m:s]: 00:000:11:15:34
Block: 1133951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336 RingCT/type: yes/0
Extra: 014e6cf1f4e15fe45c9f700f08d0bb673b2b66d80ecd73bf3f9730aadef0af67b7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98965e9ff8d6f322b83d4a265a42da091d405d77b8a6debdc6bb9770556ce3a 0.600000000000 1617174 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": 1133961, "vin": [ { "gen": { "height": 1133951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98965e9ff8d6f322b83d4a265a42da091d405d77b8a6debdc6bb9770556ce3a" } } ], "extra": [ 1, 78, 108, 241, 244, 225, 95, 228, 92, 159, 112, 15, 8, 208, 187, 103, 59, 43, 102, 216, 14, 205, 115, 191, 63, 151, 48, 170, 222, 240, 175, 103, 183, 2, 17, 0, 0, 0, 3, 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