Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfe584607a7b5431bb5ae5d2cf69e2a8bab51f4f93f5b38bd19c1737a29a19d

Tx prefix hash: d371a4fd0fa487c0009f7a5c9a0f48f4797ae96f6b48c87dd35d8466cafee1a8
Tx public key: 68fc5bafaa3618a62575b9a97de383a1bf25b02d2b739a7a33458b092c45c51b
Timestamp: 1728667251 Timestamp [UCT]: 2024-10-11 17:20:51 Age [y:d:h:m:s]: 00:236:03:40:31
Block: 1129412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168618 RingCT/type: yes/0
Extra: 0168fc5bafaa3618a62575b9a97de383a1bf25b02d2b739a7a33458b092c45c51b02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98bb80bf575556748a99bad696d3f63bdac7f9da5461875abe30cb0e5594f119 0.600000000000 1612239 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": 1129422, "vin": [ { "gen": { "height": 1129412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98bb80bf575556748a99bad696d3f63bdac7f9da5461875abe30cb0e5594f119" } } ], "extra": [ 1, 104, 252, 91, 175, 170, 54, 24, 166, 37, 117, 185, 169, 125, 227, 131, 161, 191, 37, 176, 45, 43, 115, 154, 122, 51, 69, 139, 9, 44, 69, 197, 27, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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