Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1394bfb82402d6716e78da8cae0a585beba099d8d9703d2494519dae0ba51408

Tx prefix hash: 1c4c9ef555dee52e15791d11f8cc16a9554607e877545faf10e819fa34a84402
Tx public key: 2ed9d97e543e6a8ec3a8975f999f2d7ea414154d18ef1f2aa94642652275dfb8
Timestamp: 1716092985 Timestamp [UCT]: 2024-05-19 04:29:45 Age [y:d:h:m:s]: 00:236:11:19:23
Block: 1025165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169238 RingCT/type: yes/0
Extra: 012ed9d97e543e6a8ec3a8975f999f2d7ea414154d18ef1f2aa94642652275dfb80211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a8e714ed050ee77b95fa53a7a21f168c83cdcd9142944f79fc9f1f92afa671 0.600000000000 1491464 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": 1025175, "vin": [ { "gen": { "height": 1025165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a8e714ed050ee77b95fa53a7a21f168c83cdcd9142944f79fc9f1f92afa671" } } ], "extra": [ 1, 46, 217, 217, 126, 84, 62, 106, 142, 195, 168, 151, 95, 153, 159, 45, 126, 164, 20, 21, 77, 24, 239, 31, 42, 169, 70, 66, 101, 34, 117, 223, 184, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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